The Bones

What essentials held everything together while we were stretched?

Our automated deployment pipeline meant no one had to babysit releases manually.
Daily 10-minute standups kept us aligned even though half the team was out.
Clear on-call rotation meant incidents never fell through the cracks.
The Hauntings

What stressed us out or kept coming back to spook us?

We had a single point of failure — only one person knew how the billing system worked.
Constant context switching between tasks left me exhausted.
I was terrified something would break while our only backend dev was away.
Dead Weight

What could we drop without anyone noticing or missing it?

The weekly status report nobody actually reads.
Maintaining that legacy feature only two customers still use.
A recurring sync meeting that could easily be an async update.
Raising the Dead

What should we revive or change before the next lean stretch?

Let's cross-train at least two people on every critical system.
Create a lightweight 'lean mode' playbook for when capacity drops.
Automate the deployment checklist before the next holiday season.

What is the Skeleton Crew Retrospective

Running with a skeleton crew means doing more with less — covering critical work while half the team is on leave, between hires, or pulled onto other priorities. The Skeleton Crew Retrospective gives your team a structured, slightly playful way to reflect on those periods when capacity was tight, energy was running low, and only the essentials kept the lights on. It helps surface what truly mattered, what got dropped without consequence, and how the team coped under pressure. Built around a Halloween-inspired theme, this format keeps things light while tackling a serious topic: sustainable workload and prioritisation. By exploring which "bones" of your process held the structure together, what felt like dead weight, and where the team was haunted by stress or single points of failure, you uncover practical insights about resilience, delegation, and focus. It's a great way to learn from a stretched period rather than simply surviving it. Whether you're emerging from a holiday season, a hiring gap, or an unexpectedly busy sprint, this retrospective turns a draining experience into actionable lessons. Run it in TeamRetro to capture ideas, group recurring themes, vote on what to fix, and walk away with clear actions that make the next lean stretch far less scary for everyone involved.

Skeleton Crew retrospective format

The Bones

What essentials held everything together while we were stretched?

This topic captures the core structure that kept the team standing during a lean period — the critical tasks, people, and processes that genuinely mattered. Encourage participants to name the 'load-bearing' elements they were grateful for, so the team knows what to protect next time capacity is tight.

The Hauntings

What stressed us out or kept coming back to spook us?

Use this topic to surface recurring pain points, anxieties, and the ghosts that haunted the team while running lean. These are the things that drained energy or caused worry. Frame it as identifying what to exorcise so it doesn't return during the next stretched period.

Dead Weight

What could we drop without anyone noticing or missing it?

This topic helps the team identify low-value work, ceremonies, or commitments that consumed effort without delivering proportional value. Encourage honesty — being lean is a great filter for what's truly essential. Capture candidates the team could permanently cut or pause.

Raising the Dead

What should we revive or change before the next lean stretch?

This forward-looking topic turns reflection into action. Ask the team what they want to bring back to life, set up, or improve so the next skeleton-crew period is smoother. Focus on concrete, ownable actions around cross-training, automation, and prioritisation.

When to use this retrospective

  • After a holiday season or period when a large portion of the team was on leave and you ran on minimal staffing.
  • During a hiring gap or after departures when the remaining team had to cover critical work.
  • Following an unexpectedly busy sprint where the team had to ruthlessly prioritise essentials.
  • When you want to identify single points of failure and build resilience before the next lean period.
  • As a themed seasonal retrospective around Halloween to keep engagement high while tackling workload.

Suggested icebreaker questions

  • If you were a Halloween character during our busiest week, which one would you have been and why?
  • What's the one task you'd happily bury six feet under and never deal with again?

Ideas and tips for your retrospective meeting

  • Set a psychologically safe tone — running lean is stressful, so make it clear the goal is to learn, not to assign blame for what slipped.
  • Lean into the Halloween theme to keep things light, but make sure the actions that come out are concrete and owned.
  • Give quieter or part-time members space to contribute, since they may have covered unusual tasks and hold valuable perspective.
  • Watch for survivorship bias — celebrate what worked, but dig hard into the hauntings and single points of failure that could bite next time.
  • Timebox each topic so the conversation doesn't dwell only on negatives; aim to spend real time on the 'Raising the Dead' actions.
  • Prioritise and vote on improvements so the team commits to a small number of high-impact changes rather than an overwhelming list.

Frequently asked questions

When should I use a Skeleton Crew Retrospective?
Use it after any period when your team ran with reduced capacity — such as a holiday season, hiring gap, or unusually busy stretch — to learn what kept things running and what needs fixing before the next lean period.
How long does a Skeleton Crew Retrospective take?
It typically runs in 45 to 60 minutes, allowing time to brainstorm across the four topics, group themes, vote on priorities, and agree on a few concrete actions.
How is it different from a standard sprint retrospective?
While a sprint retrospective reviews general progress, the Skeleton Crew format specifically focuses on operating under reduced capacity — surfacing single points of failure, prioritisation decisions, and resilience lessons.
What are the four topics in this retrospective?
The Bones (essentials that held everything together), The Hauntings (recurring stress points), Dead Weight (work to drop), and Raising the Dead (changes to make before the next lean stretch).
Is this only a Halloween retrospective?
The theme is Halloween-inspired and works perfectly for that season, but the underlying focus on lean operations and team resilience makes it useful any time your team is stretched thin.
Who should facilitate a Skeleton Crew Retrospective?
A Scrum Master, team lead, or any facilitator can run it. The key is setting a safe, blame-free tone so the team can openly discuss what was hard during the stretched period.

New to retrospectives? Read our guide on how to run a retrospective →